I frequently when doing a series of ./mach try perf runs have to go and manually trigger/retrigger tests on the base build (perhaps because I've changed which tests I'm triggering?)

:jesup, can you try rebasing your code and see if it still happens? I thought I had resolved this issue here, but maybe not: bug 1831603

We cache the base commit for 2 weeks, and before that patch landed it wasn't considering the tasks you selected but now it does. Note that it still won't handle retriggers that you request on it, but you can do that through the compare view (there's a column for it on the right-hand side).

I'll see if I can repro this again

Ok, so if you look at https://treeherder.mozilla.org/jobs?repo=try&revision=cec4c6867b8391f4c0dcf0f57d93f80ef83fdfbc and https://treeherder.mozilla.org/jobs?repo=try&revision=dc45fa49cdbf14b04137b20819703e8b360bce7f, there doesn't seem to be any base runs made, so I can't compare.

https://hg.mozilla.org/try/rev/f03b9d662c26741ece9e079d9199df1662f492a1 seems to have triggered https://treeherder.mozilla.org/jobs?repo=try&revision=6fe00c1acc6fefe3cd2c7b20e72c4af93cc9a778 though

:jesup, can you provide the full log of one of these mach try perf runs? I'm wondering if it produced a compare view link, and what base revision it selected.

It happened to me too, but only when I change the after commit and I don't rebase (basically, it won't push again an identical push with the previous one).

:jesup, is this bug still an issue for you? If so, could you provide some logs the next time you hit it (see comment #4).

See comment #6.

If this happens again, I'll re-report with more info